server/sstate.c, NEWS.adoc: wait a second before declaring UPS data stale#3170
Merged
Conversation
…tale [networkupstools#661] Signed-off-by: Jim Klimov <jimklimov+nut@gmail.com>
jimklimov
added
enhancement
Connection stability issues
|
Dist and Docs NUT-tarballs-PR-3170.zip are available for commit 543f294 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Addresses one guess for issue #661 (fractional/whole second rounding maybe being the problem with inter-process communications, so we wait for
MAXAGE+1now before declaring data stale).That situation may have other driver/device specific reasons when the stale/OK status flips because the driver explicitly says so (not due to timeout of comms between driver and data server, or total lack of updates for too long), as detailed in recent posts to that issue.